User profile and geolocation for efficient transactions

ABSTRACT

Techniques for providing friction-free transactions using geolocation and user identifiers are described herein. These techniques may ascertain a user&#39;s location based on a location of a mobile device. A transaction between the user and a merchant may be completed with zero or minimal input from the user based on the geolocation of the mobile device and the user identifiers. In some implementations, a transaction initiated earlier is completed when the mobile device arrives at the merchant. Additionally, a parent-child or similar relationship may be established between multiple devices. Security on the mobile device based may be provided by biometric identification and calculation of variance from regular movement patterns. Advertisements may be sent to the mobile device based on bids from merchants near to the mobile device. Promotions may be sent to the mobile device when more than a threshold number of mobile devices are located at the same merchant.

RELATED APPLICATIONS

This application is a continuation and claims priority to pending U.S.patent application Ser. No. 13/027,913 filed Feb. 15, 2011 entitled“User Profile and Geolocation for Efficient Transactions” and claimspriority to pending U.S. patent application Ser. No. 12/820,672 filedJun. 22, 2010 entitled “User Profile and Geolocation for EfficientTransactions” which claims priority to U.S. Provisional Application Nos.61/316,527 filed on Mar. 23, 2010 and 61/351,743 filed on Jun. 4, 2010all of which are incorporated by reference herein in their entirety.

BACKGROUND

The widespread use of mobile phones and the increasing sophistication ofsmart phones have created societies in which personal, mobile computingpower has become nearly ubiquitous. Content for mobile computing deviceshas typically flowed from technology initially used with desktopcomputers. Some aspects of mobile computing devices, such as a smallform factor with limited display capabilities and a lack of full-sizekeyboards, hinder adoption of content originally designed for desktopcomputers. Other aspects, such as the mobility itself, provide uniqueopportunities to use mobile computing devices in ways very differentthan the ways people use desktop computers. Development of content thatrecognizes the limitations while taking full advantage of the uniqueaspects of mobile computing devices is still an active and maturingfield.

Consumers are also becoming increasingly comfortable with virtualinteractions, such as online shopping. However, in spite of the relativeconvenience of the virtual world, as opposed to the brick-and-mortarworld, friction and security concerns still limit adoption of virtualinteractions. For example, remembering passwords and maintainingmultiple accounts create friction in virtual-world interactions.Additionally, the anonymity and lack of direct interaction between theconsumer and the merchant create potential security problems.Accordingly, content designed specifically for mobile computing devicesthat eliminates the friction of transactions and addresses securitiesconcerns will have great value for consumers.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1 shows an illustrative architecture for facilitating efficienttransactions between a user of a mobile device and a merchant based onthe geolocation of the mobile device.

FIG. 2 shows the mobile device from FIG. 1 in greater detail.

FIG. 3 shows the server(s) from FIG. 1 in greater detail.

FIG. 4 shows the user information, merchant profiles, and advertisementdatabase from FIG. 1 in greater detail.

FIG. 5 is a flow diagram of an illustrative process for automaticallycompleting a transaction between a user of a mobile device and amerchant.

FIG. 6 is a flow diagram of an illustrative process for completing apurchase by sharing information about the mobile device user with amerchant.

FIG. 7 is a flow diagram of an illustrative process for setting up amobile device to conduct low-friction (e.g., zero-interaction orsingle-interaction) transactions with a merchant.

FIG. 8 shows an illustrative architecture for a user of a mobile deviceto complete a transaction with a merchant upon arrival at thegeolocation of the merchant.

FIG. 9 is a flow diagram of an illustrative process for completing atransaction with a merchant when a mobile device and the user of themobile device arrives at the merchant.

FIG. 10 shows an illustrative architecture for conducting transactionsbetween a child device and a merchant mediated by a parent device.

FIG. 11 is a flow diagram of an illustrative process for completing atransaction between a child device and a merchant and transmitting anindication of the transaction to a parent device.

FIG. 12 shows an illustrative map of temporal-geo-locations of a mobiledevice during a workday of a user of the mobile device.

FIG. 13 is a flow diagram of an illustrative process for securing amobile device based on variance from a map of temporal-geo-locations.

FIG. 14 is a flow diagram of an illustrative process for securing amobile device based on biometric data.

FIG. 15 shows an illustrative architecture for providing merchantadvertisements or promotions to mobile devices at or near the merchant.

FIG. 16 is a flow diagram of an illustrative process for presentingadvertisements on a mobile device based on bids submitted by merchants.

FIG. 17 is a flow diagram of an illustrative process for providing apromotion to mobile devices when a number of mobile devices at amerchant exceeds a threshold.

DETAILED DESCRIPTION

Many activities are defined in whole or part by the location at whichthose activities occur. In some instances, the activity can be inferredwith a high likelihood of accuracy based on the location alone. Forexample, a car at a tollbooth is likely there to pay the toll and passthrough, a person waiting by a boarding gate for an airplane is likely aticket holder for the flight, a person with a reservation at a hotel islikely going to check in to the hotel when he or she arrives in thelobby. At some locations many types of activities may be probable, butthere are certain activities that will only happen at those locations.For example, many things may happen at the entry to a house, but armingor disarming a home security system will only be done at that location.A mobile computing device that is location-aware and can predict orinfer what a user may be doing at that location will be able to automatesome activities and provide a high level of user convenience.

This disclosure is directed to, in part, facilitating transactions basedon geolocation and unique user identification. For instance, thesetransactions may include electronic commerce transactions or any othertype of transaction. Innovations in electronic commerce, such as aone-click shopping cart, have made the “Internet shopping” experiencesmoother and have reduced friction perceived by the user. For instance,clicking a single button to complete a purchase requires fewer stepsthan entering a password, address, credit card number, and such. Thereduction of steps, clicks, and the like reduces the friction in atransaction. Commerce in the brick-and-mortar world causes the consumereven more friction than transactions in the electronic commerce world insome instances. For example, describing the item one wishes to purchase,presenting payment to a cashier, waiting for the cashier to process thepayment, and eventually receiving the desired item is an example of atypical, and relatively high-friction, brick-and-mortar transaction.

Access to the World Wide Web from mobile devices provides a platform forelectronic commerce similar to Internet shopping from a desktopcomputer. Mobile computing devices, such as mobile phones, are oftencarried with users throughout their daily interactions in thebrick-and-mortar world. Many of these mobile computing devices areequipped with Global Positioning System (GPS) functionality to determinea location of the device, and thus, a location of the correspondinguser. This disclosure combines the location awareness of mobile deviceswith the relatively lower friction transactions of electronic commerceto create a friction-free or, in some instances, a “zero-click” solutionfor interactions between consumers and merchants in the brick-and-mortarworld. Unique user identification provides a thread that ties togetherinformation about a particular user (e.g., credit card data), a linkbetween that user and a given mobile computing device, and therelationship that user wishes to have with a given merchant (e.g., optin to zero-click purchasing).

A merchant may include any human or legal person such as, but notlimited to, sellers of goods or services that engages in transactionswith customers. For example, a government may be a merchant in thecontext of providing government services, privileges, and/or rights.

The described techniques for low-friction or friction-free transactionsmay be implemented in a number of ways and in a number of contexts.Example implementations and context are provided with reference to thefollowing figures, as described below in more detail. It is to beappreciated, however, that the following implementations and contextsillustrative of many possible implementations and contexts.

Illustrative Environment and System Architecture

FIG. 1 shows an illustrative architecture 100 in which a representativeuser 102 employs a mobile device 104 to interact with a merchant 106.The merchant 106 may comprise a point-of-sale device 110 (e.g., a “cashregister”) and a merchant server 108. In some implementations, there maybe one merchant server 108 for several point-of-sale devices 110. Themerchant server 108 may also include merchant applications that manageinteractions between the merchant 106 and the mobile device 104. Themerchant applications may include applications that regulatepoint-of-sale transactions, online transactions, the provisioning ofadvertisements, promotions, information, and the like. The merchantserver 108 may also store customer information about past or potentialfuture customers. In some implementations, the customer information maycomprise information such as personal information about the customer,customer preferences, and the like.

The mobile device 104 may be implemented as any number of mobiledevices, including but not limited to a mobile phone, a personal digitalassistant (PDA), a laptop computer, a net book, an eBook reader, apersonal media player (PMP), a portable gaming system, an automobilenavigation system, and so forth. The device 104 is location aware, or isable to provide information to another entity (e.g., a server) to allowthe other entity to determine a location of the device 104. A locationon the surface of the earth, or a “geolocation,” may be provided to thedevice by a satellite 112 such as a GPS satellite. Alternatively,wireless signals such as from a radio antenna 114 may be used todetermine a geolocation of the device 104 relative to a known positionof the radio antenna 114. Other technologies and methods for determininggeolocation are also envisioned within the scope of this disclosure suchas, for example, calculating geolocation based on a network access point(e.g., WiFi hotspot) or from a locator signal broadcast from a knownlocation, such as at the merchant 106.

The device 104 and the merchant 106 may connect to a network 116. Thenetwork 116 may include any one or combination of multiple differenttypes of networks, such as cable networks, local area networks, personalarea networks, wide area networks, the Internet, wireless networks, adhoc networks, mesh networks, and/or the like. In some implementationsthe satellite 112 and/or the radio antenna 114 may provide networkconnectivity to the mobile device 104 as well as provide geolocation.For example, the radio antenna 114 may provide network access to themobile device 104 according to the International MobileTelecommunications-2000 standards (“3G network”) or the InternationalMobile Telecommunications Advanced standards (“4G network”). Otherimplementations may include one source of geolocation data such as thesatellite 112 and a separate source of network connectivity such as aWiFi hotspot. The merchant 106 may connect to the network 116 throughthe merchant server 108 using any suitable mechanism such as a wired orwireless connection.

A one or more servers 118 may also be connected to the network 116 andconfigured to manage interaction between the mobile device 104 and themerchant 106. In some implementations, all or part of the interactionbetween the mobile device 104 and the merchant 106 may be through adirect communications link 120 without passing through the server 118 orthe network 116. The direct communication link 120 may be implemented byradio transmissions (e.g., IEEE 802.11, Bluetooth), infrared signals,radio frequency identification (RFID), magnetism (e.g., magnetic stripssuch as used on credit cards), display of a code on the device 104 to ahuman operator or to a scanning device at the merchant 106, and/or anyother method of directly passing information between the mobile device104 and the merchant 106.

The server(s) 118 may house or otherwise have a connection to multipledata stores including user information 122, merchant profiles 124, anadvertisement (“ad”) database 126, and/or other data stores. Generally,the user information 122 contains information about the user 102associated with the mobile device 104. The user information 122 enablesefficient and personalized interaction between the user 102 and themerchant 106. The merchant profiles 124 generally contain informationabout one or more merchants including the merchant 106 with which theuser 102 is interacting. One type of interaction between the merchant106 and the user 102 is advertising provided from the merchant 106 tothe device 104. Information for generating relevant advertisements maybe contained in the advertisement database 126. Each of the data storeswill be discussed in greater detail below.

The server(s) 118 may also comprise an authentication module 128 thatcompares login information from the mobile device 104 and/or themerchant 106 to confirm that the correct user information 122, merchantprofiles 124, advertisement database 126, and other information iscorrectly correlated with the right entity (e.g., user 102 and/orpoint-of-sale device 110). The authentication module 128 will bediscussed in greater detail below.

Illustrative Mobile Device

FIG. 2 is a schematic representation of the mobile device 104 of FIG. 1.The mobile device 104 includes one or more processors 202 and a memory204. The memory may contain a user identification module 206 that inturn contains a user identifier 208, user information 210, a transactionmodule 212, and a security module 214. The user identification 208 maybe a unique number or code that uniquely identifies the user 102 of themobile device 104. This user identification 208 may be the same useridentification 208 that the user 102 uses for interacting with onlinemerchants and the like. In some implementations, the user identification208 may be entered by the user 102 into the mobile device 104 during asetup procedure such as by entering a user name and a password. In otherimplementations, the user identification 208 may be included in hardwareof the mobile device 104. For example, a unique serial number of themobile device 104 may be linked with a user name and password when theuser 102 purchases the device 104. As a further example, a subscriberidentification module (SIM) on a removable SIM card within the device104 may contain the user identification 208. In this example, the useridentification 208 may be transferred between devices by moving the SIMcard.

The device 104 may also contain user information 210 stored locally inthe memory 204. This information may be configurable by the user 102 andcan include payment information, a home location, and/or map of thedevice's 104 past movements, past transaction histories, and/or anyother information related to the user 102.

The transaction module 212 may recognize when the mobile device 104 islocated at a merchant location and, in response, may facilitate atransaction with the merchant 106. The transaction may be based in parton the user information 210. The transaction module 212 may beconfigured with appropriate application programming interfaces (APIs) toestablish a standard communication protocol for receiving informationfrom the merchant 106 (e.g., merchant name and requested payment) andproviding corresponding information about the user 102 (e.g., paymentinformation and user identification 208). In some implementations, thetransaction module 212 is a software application that a user 102 mayinstall on his or her device 104 such as by downloading from a website.In other implementations, the transaction module 212 may be preinstalledby a manufacturer or retailer of the mobile device 104 and/or built intothe mobile device 104 as a type of firmware or hardware. The transactionmodule 212 coordinates the user identification 208, user information210, geolocation, and the like to facilitate transactions between theuser 102 and the merchant 106.

Given the ability of the mobile device 104 to serve as a platform forzero-click purchases, there is a need to provide security in order toprevent unauthorized charges. The security module 214 addresses thisneed by limiting functionality of the mobile device 104 and initiatingsecurity events in appropriate circumstances. The security module 214may process login information, such as passwords and/or biometricinformation to authenticate the user 102 and prevent other people fromusing the mobile device 104. The security module 214 may also analyzebehavior such as purchasing patterns and/or movement patterns and inferthat irregular behavior may indicate fraudulent or unauthorized activityand limit device functionality accordingly, as described below ingreater detail.

Mobile device 104 also includes one or more input and output devices216. The output devices may comprise one or more display devices 218including touch-screen displays that also function as an input device.An accelerometer 220 detects rotation or vibration of the mobile device104. The accelerometer 220 may be a convenient mechanism for the user102 to communicate an input to the mobile device 104 by slapping,shaking, twisting, and/or by making a motion that can be detected by theaccelerometer 220. The mobile device 104 may also include a camera 222capable of taking still or video pictures. An antenna 224 in the mobiledevice 104 may send and receive wireless signals from sources such asthe radio antenna 114 and satellite 112. The device 104 may furthercomprise other input/output devices 226, such as a microphone and aspeaker used, for example, in an implementation in which the mobiledevice 104 functions as a telephone.

In some implementations, the mobile device 104 may also include acalendar/clock 228, a location sensor 230, and a network interface 232.The calendar/clock 228 may calculate time, date, and other data that canbe derived from time data and date data. In some implementations, thecalendar/clock 228 may communicate with the location sensor 230 todetermine, for example, day length at the current location of the device104 based on the date. This could enable the device 104 to determinewhether it is daytime or nighttime based on the time, date, andgeolocation.

The calendar/clock 228 and the location sensor 230 may also communicateto create a log of where the device 104 is located at numerous timepoints. The log of time-place data may be compiled into a map that showsmovements of the device overtime and throughout different dates. Thismap may be stored in the memory 204, for example as a part of the userinformation 210. The location sensor 230 includes any sort of systemthat informs the mobile device 104 of its geolocation including, but notlimited to, the Global Positioning System of satellites circling theEarth. Alternatively, the location sensor may determine geolocation byradio signal triangulation (e.g., triangulation based on radio antennasignal strength).

The network interface 232 may be configured for wirelessly communicatingwith the network 116. The network interface 232 may use any standardprotocols for network communication. The network interface 232 may becapable of high speed, wireless network communication. In someimplementations, the network interface 232 may use the antenna 224 tosend and receive data from the network 116. In further implementations,a network interface 232 may provide information to the location sensor230 (e.g., a closest network access point) from which the locationsensor 230 can infer or calculate a location of the mobile device 104.

Illustrative Server

FIG. 3 is a schematic representation of the server(s) 118 of FIG. 1. Theone or more servers 118 may be implemented as a single computing device,a server farm comprising multiple servers, a distributed network, acloud-computing configuration, and/or the like. The server(s) 118comprises one or more processors 302 and a memory 304. The memory 304may contain the same user identifier (1) 208 associated with the mobiledevice 104 FIG. 2. In some implementations, memory 304 may containthousands or even millions of separate user identifiers represented hereas User ID (N) 306 where N is any number greater than one. Each useridentifier may be associated with a respective mobile device.

The user identifier 208 represents a user 104 that is interacting withthe server(s) 118 via a mobile device 104. The authentication module 128determines if communications coming from the mobile device 104 should beassociated with the user identifier 208. In some implementations,authorization may involve handshaking or other verification between, forexample, the authentication module 128 of the server(s) 118 and thesecurity module 214 of the mobile device 104. The authentication module128 may similarly authenticate the identity of merchants 106. Providingrobust data security may avoid fraudulent transactions from both mobiledevices 104 and merchants 106.

The server(s) 118 may also include a transaction module 308. In someimplementations, the transaction module 308 on the server(s) 118 issimilar to the transaction module 212 on the mobile device 104.Transactions between the user 102 and the merchant 106 may befacilitated by either or both of the transaction modules 212 and 308when a geolocation of the device matches or is within a thresholddistance of a geolocation of the merchant. The transaction module 308may be configured with APIs for exchanging information with both themerchant 106 and the mobile device 104. In some implementations, theAPIs exposed to the merchant 106 may be regulated to preventunauthorized merchants from access in the system and to improve datasecurity. The APIs exposed to the mobile device 104 may be generic orcustomized to specific device hardware and operating systems. Providingmultiple sets of APIs may allow the server(s) 118 to translatecommunications between mobile devices 104 and merchants 106 that wouldotherwise not be able to exchange information.

A map 310 stored on the server(s) 118 may contain geolocations ofmerchants 106. Correlation between a particular merchant 106 and aparticular geolocation may be used to infer that a mobile device 104 islocated at or near a merchant 106 because the mobile device is locatedat or near a geolocation associated with that merchant 106 in the map310. The map 310 may also contain real-time information about thegeolocations of each of the mobile devices 104 associated with therespective user identifiers 208-306. From this information it may bepossible to determine how many mobile devices 104 that belong to thesystem are present at a given merchant location. It may also be possibleto identify other mobile devices 104 in proximity to a given mobiledevice 104. For example, the map 310 may show that a user's friend (orat least the friend's mobile device) is at the merchant next door.

The server(s) 118 may also facilitate advertising via advertisementssent from or on behalf of the merchant 106 to the mobile device 104. Insome instances, the bidding module 312 may receive and process bids forthe privilege to place advertisements on mobile devices 104. Users 102may opt in to receive advertising and be presented with relevantadvertisements based on a geolocation of the mobile device 104 and userinformation 122. The bidding may be structured according to any knownbidding system or otherwise. The operator of the server 118 maystructure the bidding so as to maximize advertising revenue paid by themerchants 106.

FIG. 4 shows multiple data stores including user information 122,merchant profiles 124, and an advertisement database 126 that may beincluded within or connected to the server(s) 118. The user information122 may contain some or all of the same information stored as userinformation 210 on the mobile device 104. In some implementations, theuser information 122 stored on the server(s) 118 may be used to backupor restore the user information 210 on the mobile device 104 if, forexample, the mobile device 104 is lost or damaged. The user information122 may provide separate data associated with each of the useridentifiers 208-306 shown in FIG. 2. For example, User ID (1) 208 may beassociated with payment information 402, a user profile 404, atransaction record 406, and a list of trusted merchants 408. The paymentinformation 402 may include such things as credit card or debit cardnumbers, bank account information, electronic payment systeminformation, and/or the like. The user profile 404 may contain userpreferences, lists of interests and hobbies, indications of which typesof communications and/or transactions the user 102 has selected toreceive, personal information such as preferences for a matchmakingservice, and any other type of information associated with the user 102and his or her User ID (1) 208. The transaction record 406 may contain alist of past transaction history comprising the merchant, time,geolocation, and subject of the transaction.

Out of all the merchants participating in the system the user 102 mayselect some subset of those merchants as trusted merchants 408. In someimplementations, whenever a user conducts a transaction with a merchantthe user may be asked if he or she wishes to add that merchant to thelist of trusted merchants. This status as a trusted merchant may be partof the user information 122. The status as a trusted merchant may enablethe merchant 106 to engage in transactions with the user 102 via theuser's mobile device 104. The status as a trusted merchant may alsodecrease the amount of interaction required from the user 102 tocomplete electronic transaction using the mobile device 104 as comparedwith other merchants that are not included on the trusted merchant list.Within the list of trusted merchants 408 different merchants may begiven different trust levels by the user 102. For example, transactionswith the most trusted merchants may be completed automatically merely bythe user 102 (and the mobile device 104) entering a location of themerchant 106. For other merchants 106 with whom the user 102 does notdesire such use of “zero-click” transactions, the user 102 may indicatea lower level of trust that requires some minimal interaction betweenthe user 102 and the mobile device 104 in order to complete atransaction. This may be thought of as a “one-click” interaction,although the specific interaction may be something other than a “click.”For other merchants that the user 102 associates with an even lowerlevel of trust, the user 102 may require more than one click such asentry of a password and login before the mobile device 104 is enabled tocomplete a transaction with the merchant 106.

The merchant profiles 124 contain information about the merchants suchas geolocations 410 of the merchants' brick-and-mortar locations,promotions 412 offered by the merchant, and other data 414 about themerchant which may be used to facilitate transactions with mobiledevices 104 (e.g., types of credit cards are accepted). The geolocations410 may be one source of data used to create the map 310 stored on theserver(s) 118. The promotions 412 may include things such as coupons ordiscounts for goods or services offered by the merchant. The promotions412 may, for example, give a discount to a user 102 who has designatedthe merchant as a trusted merchant. As a further example, a merchant mayprovide a coupon to a user 102 of a mobile device 104 when the userenters a competitor's store.

Communication between merchants and mobile devices 104 may also includeadvertising. The mobile device 104 may have a user interface with adesignated window or advertisement box for displaying advertisementssent from merchants 106. The advertisement database 126 storesadvertisement content 416 in association with geolocations 418 andmerchant information 420. Because the advertisements are targeted formobile devices 104 which may include a location sensor 230, theadvertisement content 416 is associated with one or more geolocations418 in order to provide location-relevant advertisements. For example,advertisements for a merchant may appear when the user 102 carrying themobile device 104 approaches the geolocations of one of the merchant'sretail stores. For instance, when a user approaches a coffee shop, thatcoffee shop may serve an advertisement or a promotion for a discountedcup of coffee when the user is near to or is within the coffee shop.

The advertisement content 416 may appear when the mobile device 104 is apredetermined distance from the merchant. In some implementations, thepredetermined distance may depend upon a speed at which the mobiledevice 104 is traveling so that someone traveling in a moving car mayreceive the advertisement content 416 at a greater distance from themerchant then someone walking. In some implementations, the display ofadvertisements may be deactivated based on the speed at which the mobiledevice 104 is moving. This feature could prevent distractions to driversby blocking advertisements, or at least placing the mobile device into asilent mode, when the speed of the mobile device 104 exceeds a speedthreshold. The merchant information 420 may designate the merchantsupplying the advertisement content 416. This may be used in conjunctionwith the user profile 404 of a user 102 to provide advertisements frommerchants from which that user 102 has expressed an interest (explicitlyor implicitly), while refraining from providing advertisements fromother merchants. The merchant information 420 may also contain a bidamount indicating a maximum amount that the merchant is willing to bidin order to “win” and display their advertisement on the user's mobiledevice. This bid amount may be used by the bidding module 312 todetermine which advertisement content 416 is displayed on a given mobiledevice 104.

Illustrative Transactions Between a Merchant and a Mobile Device

FIG. 5 illustrates a process 500 that includes associating, at operation502, user information with a device. The user information may comprise,for instance, the user information 122 illustrated in FIG. 1. In someimplementations, the device may be the mobile device 104 illustrative inFIG. 1. Associating user information with the device ties the identityof the user to the device and allows the device to represent the user insome electronic transactions. Next, at operation 504, the location ofthe device is determined. As described above, the location may bedetermined by a location sensor 230 that determines a geolocation asillustrated in FIGS. 1 and 2.

Operation 506 then correlates the location with a merchant. The merchantmay, for example, provide a wireless network connection inside orproximate to its premises and the connection may identity the merchant.By doing so, each device using that network connection may recognize itscurrent location as being at the merchant. In some implementations, thedevice may additionally or alternatively be aware of an abstractlocation such as a latitude and longitude provided by GPS. A map ofmerchant locations 508 may be used to match the latitude and longitudeof the device with a merchant location. There may be locations at whichthe geolocation of the device can be identified; however, thatgeolocation might not correlate with any merchant location. For example,the device may be on a street near to several merchants but not locatedat any of those merchants.

At decision point 510 it is determined if the device is located at themerchant. In some instances, this determination may include determiningif the device is within the merchant, while in other instances this mayinclude determining if the device is within a predetermined distance ofthe merchant. If not, process 500 follows the “no” path and returns tooperation 504. This loop may repeat continually until the device islocated at a merchant. When the device is located at a merchant, process500 follows the “yes” path to decision point 512.

At decision point 512, it is determined if transactions with thismerchant are automated. For example, the user may decide that he or shewants to complete certain types of transactions with certain types ofmerchants in an automated manner. In such situations, the user mayactivate an automatic transaction functionality of his or her mobiledevice. However, for other merchants, or for other types oftransactions, the user may desire more interaction such as specifyingthe details of the transaction or affirmatively agreeing to thetransaction. If this transaction with this merchant is not automated,process 500 follows the “no” path and returns to operation 504. If thetransaction is automated then process 500 follows the “yes” path tooperation 514.

At operation 514 a transaction between the user of the device and themerchant is completed automatically in some instances. This automaticcompletion of the transaction when the user is located at the merchantcreates a friction-free experience for the user. The coupling oflocation awareness with a mobile computing device allows for zero-clicktransactions.

As one illustrative example, a user could associate her prepaid card (orother payment instrument) for the local coffee shop with a mobiledevice. The user could additionally set her favorite drink at thiscoffee shop as a tall latte. This information may be stored on themobile device, such as user information 210, or somewhere on a network,such as user information 122. The local coffee shop may have many storesand each store location may be associated with unique latitude andlongitude coordinates. When the user carrying her mobile device arrivesat any of the store locations the device recognizes those coordinates ascorresponding with the local coffee shop and implements a transactionspecified by the user. In this example, the user can specify that themobile device uses her prepaid card to purchase a tall latte whenevershe enters one of the local coffee shop locations. The user can walkdirectly to the counter and pick up her tall latte without opening herwallet or even verbally placing an order. This is a friction-freetransaction. This example may take several variations. For instance, themerchant may ask the user to show an identification of the user (e.g., adriver's license), to orally state a password associated with the user,or the like. Or, the user may receive a phone call or a text message andmay confirm completion of the transaction via one of these communicationchannels.

As another illustrative example, the merchant may be an ambulance thatis itself mobile with location awareness and ability to communicate withmobile devices. A portion of the user information 122 and/or 210 maycontain medical information about the user. This information may beencoded, available only through predetermined APIs, or otherwise limitedso that is only released to “merchants” that provide medical servicessuch as the ambulance. When the geolocation of the ambulance and thegeolocation of a mobile device are the same, the medical informationfrom that mobile device may be automatically provided to medical serviceproviders in the ambulance. That medical information could potentiallycontain a photo of the user so that the paramedics can confirm that theperson actually in the ambulance is the correct user to associate withthe medical information. This medical information may include, forinstance, a medical history of the user, medications that the user isallergic to, and the like, thus allowing the paramedics to properlytreat the user in the event of an emergency.

The mobile device 104 may also facilitate transactions with merchantseven when the user 102 is not at or near the geolocation of the merchant106. For example, some merchants such as an online dating/matchmakingservice may not have a physical location of relevance to users. For thistype of merchant, the point-of-sale device 110 may be a server itself ora component of the merchant server 108. In such cases, the user 102 maybe at a geolocation associated with another merchant such as arestaurant, but interact with the online merchant.

In an online dating implementation, transactions may be dependent uponthe geolocation of one user relative to another user rather than thegeolocation of the user 102 with respect to the merchant 106. Forexample, members of the online dating service may choose to make thegeolocations of their respective mobile devices available to a merchantserver of the online dating service. The merchant server may determineif two mobile devices are within a threshold distance of each other andif the two users are determined to be a match by the dating service(e.g., a match may be defined at least in part upon user information 122such as the user profile 404), a transaction may be initiated betweenone or both of the mobile devices and the online dating service. Thetransaction may comprise a notification of a “member match” to which oneof the users may respond by requesting to contact the other user who isthe “member match.” The other user receiving the contact request mayaccept the contact request, decline the contact request, or ignore thecontact request. If the contact request is accepted, the online datingservice may allow mediated contact between the two users. In someimplementations, direct contact information may be kept private so thatcommunication between the two users must go through the online datingservice (e.g., the merchant server of the online dating service).

FIG. 6 illustrates process 600 that includes detecting a presence of adevice at a merchant 602. The detection may be performed by the mobiledevice, the merchant, a network component, such as server(s) 118illustrated in FIG. 1, or a combination thereof. For example, a distanceof the mobile device from three cell phone towers may be used totriangulate a geolocation of the mobile device and that geolocation maybe used to detect that the mobile device is present at the merchant. Thedesignation of the device as present at the merchant may be contextdependent (e.g. it may depend on a neighborhood density). For example,in a dense neighborhood with lots of shops directly adjacent to oneanother “presence” may be defined by a narrow spatial boundary and arequirement that the mobile device remain within that boundary for aperiod of time such as 30 seconds, 10 minutes, one hour, etc. The timerequirement may prevent accidentally detecting the mobile device being“present” when in fact the user is merely passing by the merchant. Inother contexts, for example a tollbooth on an empty highway, the mobiledevice may be designated as “present” at the tollbooth while stillhundreds of yards away based on the speed and trajectory of the userdevice. This may allow the mobile device to pay the toll in time for thetollgate open without a vehicle approaching the tollbooth needing tosubstantially decrease speed.

At decision point 604, it is determined if the merchant is a trustedmerchant for the user. The determination may be based in part on thelist of trusted merchants 408 illustrated in FIG. 4. When the merchantis a trusted merchant, process 600 proceeds along the “yes” path tooperation 606. At operation 606, the user device logs in to themerchant. The login may be completed using the user identifier 208illustrated in FIGS. 2, 3, and 4.

At operation 608, information about the device user is shared with themerchant. The information may include payment information 610,preference information 612, and a user identifier 614. In someimplementations the user identifier 614 provided to the merchant in thisoperation may be the same user identifier 208 discussed above. In otherimplementations, the user identifier 614 in operation 608 may bedifferent such as a unique user identifier 614 for this particularmerchant, a “nickname” that is a proxy for the user identifier 614, orother identifier. Information may be shared with a point-of-sale device110 of the merchant such as illustrated in FIG. 1. The preferenceinformation 612 may indicate what type of good or service the deviceuser prefers to purchase. Returning to the coffee shop example, thepreference information 612 may indicate that the user wishes to purchasea tall latte when at that coffee shop. In the tollbooth example, thepreference information 612 may indicate that a user operates amotorcycle rather than a car, and thus, wishes to pay the appropriatetoll for a motorcycle. In some implementations, the mobile device maysimply provide the user identifier 614 to the merchant and merchant mayretrieve other information linked to the user identifier 614 (e.g.,payment information, preference information, etc.) from a communicationnetwork such as the network 116 illustrated in FIG. 1.

Next, at operation 616 the purchase between the user and the merchant iscompleted. The purchase may be completed using the payment information606. It may also be completed using preference information 612, which insome implementations, may be used to automate the purchase so that thegood or service indicated by the user preference information 612 isautomatically purchased when the mobile device is detected at amerchant. In other implementations, completing the purchase at operation616 may involve only a single interaction between the user and themobile device. For example, the user may need to press a particularnumber on a numeric key pad or a soft key on a touch screen display ofthe mobile device. Additionally, the single interaction may comprisespeaking into a microphone on the mobile device or shaking the mobiledevice to activate an accelerometer inside the mobile device. Sometransactions, meanwhile, may involve multiple interactions.

If however, at decision point 604 the merchant is not recognized as atrusted merchant, process 600 proceeds along the “no” path to operation618. At operation 618 the user is queried regarding if and how toproceed with a purchase at this merchant. For example, the user maydecline to interact with this non-trusted merchant. Alternatively, theuser may elect to login to the merchant even though it is not a trustedmerchant and proceed to complete a purchase.

FIG. 7 illustrates process 700 for setting up a mobile device tointeract with a merchant in the one or more of the manners describedabove. The user may select a merchant from a list of merchants atoperation 702. The list of merchants may include merchants that chooseto participate in this system of electronic commerce. This selection maybe performed on the mobile device or on another computing device fromwhich the list of selected merchants is then sent to the mobilecomputing device. At operation 704, a level of transaction verificationis designated for one or more of the selected merchants. The level oftransaction verification does not necessarily correspond to the trustlevels discussed above. The user may designate certain merchants withwhom he or she may complete transactions with a transaction verification(and, hence, with whom the user wishes to complete transactionsautomatically with zero interaction with his or her mobile device).Examples for which this level transaction verification may be suitableare coffee shops and tollbooths, among others. For other merchants theuser may wish to take some affirmative step to verify the transactionand will therefore designate that a single interaction (or more) withthe mobile device is to be used to verify the transaction. This may bedesirable for trusted merchants that sell relatively expensive goods orservices. For example, the user may wish to use his or her mobile deviceto pay for veterinary services, but does not want a $1,000 charge placedon to his or her account without at least a single interaction on themobile device verifying that transaction. For other merchants, it may bepossible to designate a level of transaction verification that requiresmore than a single interaction. This higher level of verification may beanything from pressing two keys on the mobile device to a complex loginprocess that includes entering a password and providing paymentinformation such as a card number.

At operation 706, user information to share with a merchant is selected.The user information may include any or all of the user information 122shown in FIG. 1 and/or the user information 210 shown in FIG. 2. Forexample, sharing the user identifier 208 with the merchant will enablethe merchant to recognize that mobile device by the user identifier 208.Additionally, the user may choose to share different information withdifferent merchants. For example, credit card information may be sharedwith one merchant while bank account information is shared with adifferent merchant.

Next, at operation 708 a transaction is initiated between the merchantand the mobile device when the mobile device is at the merchant. Thetransaction may be verified according to the level of transactionverification indicated at operation 704. As discussed above, in someimplementations, this may comprise zero interaction 710 and in otherimplementations this may comprise a single interaction 712 (or more)between the user and the mobile device. Setting up the mobile device inadvance can establish default behavior when the mobile device is presentat a merchant location. In some implementations, this setup informationmay expire after some length of time such as 24 hours. Upon expiration,the level of transaction verification may be reset to require a completelogin for every merchant or in some implementations the number ofinteractions required may be raised incrementally (e.g., zerointeraction merchants now require a single interaction, singleinteraction merchants now require at least two interactions with themobile device, etc.). In other implementations, the setup informationmay not expire but rather persists until the user makes a change.

FIG. 8 shows an illustrative architecture 800 in which a representativeuser 102 employs a device 802 to initiate a transaction that will becompleted when the user later arrives at the merchant 106. The processesshown previously in FIGS. 5-7 are generally related to transactions thatare initiated when the user 102 is at the same location as the merchant106. The architecture 800, however, is additionally applicable insituations where the user 102 may initiate a transaction at one placeand point in time and then later complete the transaction upon arrivalat the merchant 106.

The user may initiate a transaction 804 through interaction with device802. Device 802 may be the mobile device 104 or it may be a differentcomputing or communication device such as a telephone, a desktopcomputer, laptop computer, thin client, set top box, game console, orthe like. Device 802 may be connected directly or indirectly to anetwork 806. The network 806 may be the same network as network 116illustrated in FIG. 1. A user identifier 208 is associated with thetransaction 804. The user identifier 208 enables the merchant 106 tomatch transaction 804 with the correct user. Initiating that transactionmay place that transaction in a transaction queue of the merchant 106.In some implementations this transaction queue may be maintained on themerchant server 108 illustrated in FIG. 1. The transaction queue couldcontain such things as a pre-order for a cup of coffee (to be deliveredwhen the user arrives at the coffee shop) or a hotel reservation (to beconfirmed with the user checks in to the hotel). Transactions may remainin the transaction queue for some period of time (e.g., minutes ordays), but instantaneous, or nearly instantaneous, implementations arealso possible.

The user 102 later arrives at the merchant 106 with his or her mobiledevice 104. Recall that the mobile device 104 may also be associatedwith the user identifier 208 as illustrated in FIG. 2. In someimplementations, a satellite 112 provides the mobile device 104 with ageolocation that can be compared with or matched to a geolocation of themerchant 106. When at the merchant's location the mobile device 104 anda computer system of the merchant 106 can communicate directly over acommunication path 808 or indirectly via the network 806. The merchant106 may access the network 806 to retrieve the transaction 804 when themobile device 104 associated with user identifier 208 is present at themerchant location. Information provided by the merchant 106 to themobile device 104 may be used by the user 102 to complete thetransaction 804. In some implementations, completing the transaction mayinvolve the user being charged and subsequently gaining access to asecure location 810. The secure location 810 may comprise a hotel room,an airplane, a person's home, a workplace, inside the borders of acountry, or any other geolocation to which entry is regulated. Entry tothe secure location 810 may be provided by a code personalized to theuser 102. The personalized code may be stored in the user information122. For example, the code may be a series of numbers and letters thatthe user 102 wishes to re-use whenever access requires entry of a codeon a key pad or such. As a further example, the code may be based atleast in part on biometric data from the user 102. Biometric data isdiscussed below in more detail in relation to FIG. 14. In someimplementations, this code may be hidden from the merchant 106 so thatthe merchant 106 only receives the user identifier 208, but cannotaccess the user's personalized code.

For example, a user may make a hotel reservation from his home computer.The reservation along with his user identifier is transmitted across acommunication network to the computer systems of the hotel. Some time(e.g., days) later when the user arrives at the hotel and his mobiledevice is detect at the geolocation of the hotel, the user identifiercontained in his mobile device is used to retrieve the reservation.After confirming payment, such as by a credit card also linked to hisuser identifier, the hotel sends a text message or other communicationto his mobile device that contains his room number. This may happenwhile he is walking through the lobby to the elevators without everstopping at the front desk. Once at his room, the presence of his mobiledevice outside the door may be detected by a wireless communicationnetwork in the hotel and the door may be automatically unlocked. Roomkeys may be provided inside the hotel room. In implementations in whichthe user identifier is also linked to a user profile (and the user haselected to share his user profile with the hotel), the user profile maybe used to customize his guest experience at the hotel by, for example,instructing the hotel staff to place his favor type chocolate on thepillow. Similar to the purchase of goods, the system can provide afriction-free experience for the purchase of services.

As a further example, the architecture and systems described herein canbe applied to immigration and border security. In this context, thetransaction 804 may be the granting of entry to a country. Initially,the person wishing to travel to a different country may enter userinformation about the potential trip into a computing device 802 andassociate that information with the transaction 804 as well as a useridentifier 208 for the potential traveler. In some implementations, apassport number could be used as the user identifier 208. Upon arrivalat immigration in the destination country, mobile device 104 carried bythe traveler may signal to the immigration authority that this personhas arrived and is requesting entry. In some implementations, the useridentifier 208 may be associated with a mobile device 104, such as amobile phone, that the user 102 is instructed to bring when they travelto the other country. In other implementations, the mobile device 104may be a miniaturized electronic device that is attached to the user'spassport as an entry visa. In yet other implementations, the passportitself may comprise the mobile device 104 and an RFID in the passportmay be the user identifier 208. This system may reduce the frictionassociated with processing people entering a country by allowing theimmigration transaction to be partially completed in advance and byautomatically identifying the people and the corresponding informationwhen they are located at an entry point.

FIG. 9 illustrates a process 900 for completing a transaction between auser and a merchant when the user arrives at a geolocation of themerchant. At operation 902, a transaction is initiated between the userand the merchant. Initiation of the transaction may be separated inspace and in time from completion of the transaction; however, suchseparation is not necessary.

Upon arrival at the merchant's geolocation, the mobile device isdetected at the merchant in operation 904. The detection may be directsuch as implementations in which a signal broadcast by the mobile deviceis picked up by a receiver at the merchant. Alternatively, the detectionby be indirect or inferred by correlating a current geolocation of themobile device with a geolocation of the merchant. At operation 906, thepresence of the user is communicated to the merchant. The communicationmay trigger the merchant to access the transaction.

User information may be provided to the merchant at operation 908. Theuser information may be provided directly from the memory of the mobiledevice or a user identifier associated with the mobile device may beused to retrieve user information from a network or other remote datasource. As discussed earlier, the user information may include paymentinformation, a user profile, and the like. The user profile may includeuser preferences that the merchant uses to modify the transaction. Userpreferences may include such things as window or aisle seat on anairplane, smoking or non-smoking rooms in a hotel, and the like. Next,at operation 910, the transaction between the user and the merchant iscompleted. Completion may include collecting a payment, confirming areservation, making a purchase, etc.

Following completion of the transaction, at operation 912, the merchantmay send a message to the mobile device confirming completion of thetransaction. The message may be a receipt for the transaction, or insome implementations, it may be a code or other information that isnecessary to access a secure location such as a hotel room or anairplane. For example, the message may comprise a boarding pass barcodethat can be displayed on a screen of the mobile device and scanned byconventional equipment when the user boards an airplane. In otherimplementations, the message may be an electronic token that providesadditional functionality to the mobile device. For example, theelectronic token may allow the mobile device to broadcast a signal(e.g., analogous to a garage-door opener) that may be used to open adoor and gain access to the secure location.

Illustrative Parent and Child Devices

FIG. 10 shows an illustrative architecture 1000 in which a two deviceshaving a parent-child relationship interact to complete a transactionwith a merchant. While this example describes the techniques in theparent/child context, these techniques may similarly apply foremployer/employee contexts, teacher/student contexts, adult child/seniorparent, and/or any other context. This relationship may be generallythought of as a master-slave relationship between computing devices. Thechild 1002 is a user of a child device 1004. The child device 1004 maybe associated with a given user (i.e., the child 1002) based on a loginor authentication of the user on the child device 1004. In someimplementations, the login may be tied to the user information 122 ofthe child 1004 thus providing the same features, and parentally imposedlimitations, on any device that the child 1002 uses. The child device1004 may be a mobile device similar to the device 104 illustrated inFIG. 1. In some implementations, the child device 1004 may be designedwith a simple user interface, limited features, large buttons, brightcolors, and/or otherwise adapted for a younger user. A parent 1006interacts with a parent device 1008. The parent 1006 and the parentdevice 1008 may be similar to the user 102 and the mobile device 104illustrated in FIG. 1. However, the parent device 1008 may be anon-mobile device, such as a desktop computer. Although designatedherein as a “parent” and a “child” the two users may have a relationshipother than a parent-child relationship, as discussed above. However, aswill be described in more detail below the parent device 1008 may havelimited control and/or supervision functionality with respect to thechild device 1004. This hierarchical relationship between the twodevices could be implemented in an employment context as well as afamily context.

The satellite 112 and the radio antenna 114 are the same as shown inFIG. 1. The child device 1004 is aware of its geolocation, or anotherentity is able to track this geolocation. The geolocation informationmay be provided by the satellite 112, the radio antenna 114, and/oralternative sources as discussed above. The child device 1004 and theparent device 1008 share at least one communicative connection. In someimplementations, such as mobile phones, the two devices may communicatevia the radio antenna 114. In the same or different implementations, thetwo devices may have a connection to a network 1010 such as theInternet. The network 1010 may be the same as the network 116 shown inFIG. 1. In other implementations, it may be a different network such asa subset of the network 116 restricted to only content and connectionsthat are deemed suitable for a child.

The merchant 106 may also have a connection to the network 1010 overwhich information may be shared with either the child device 1004 or theparent device 1008. The child device 1004 may communicate with themerchant 106 across the network 1010 and/or communicate directly withthe merchant 106 over a direct communication link 1012. The directcommunication link 1012 may be similar to the direct communications link120 illustrated in FIG. 1.

FIG. 11 illustrates process 1100 for completing a transaction between achild device and a merchant and transmitting an indication of thetransaction to the parent device. At operation 1102, a geolocation ofthe child device is determined. The geolocation of the child device maybe determined in reference to the satellite 112 or radio antenna 114shown in FIG. 10. Next, at operation 1104 the geolocation of the childdevice is correlated to a merchant. Correlation may be accomplishedthrough any of the mechanisms discussed above such as, for example,comparing the geolocation of the child device to a map of merchantlocations. At operation 1106, a transaction is initiated between theuser of the child device and the merchant. The transaction may beinitiated automatically in some implementations, or in otherimplementations the transaction may involve one or more inputs from theuser of the child device before initiation.

An indication of the transaction is transmitted to a parent device atoperation 1108. The indication may inform the user of the parent deviceabout the details of the transaction between the child device and themerchant. In some implementations, the indication may be provided inreal-time to the parent device. A record or log of transactions of thechild device may be maintained for access by the user of the parentdevice. The log may store any combination of transactions initiated,completed, and/or denied. In some implementations the log may be similarto the transaction record 406 illustrated in FIG. 4. The log may bestored in association with the user identifier of either the parent orthe child. Depending on the level of control for parent wishes toexercise over transactions made by child, parental authorization fromthe parent device to the child device may be necessary to complete thetransaction. A requirement for parental authorization may depend on thenature of a transaction. For example, a parent may configure the systemto allow the child to purchase books without parental authorization, butto require parental authorization for purchases of candy. Additionally,or alternatively, the requirement for parental authorization may dependof a value of the transaction (i.e., dollar value), a geolocation of thechild device, and/or other factors. In one implementation, the parentmay provide the child with a budget (in terms of money or other metric)and when the child is under budget authorization may not be required,but authorization may be required for transactions that exceed thebudget. In situations for which parental authorization is required, theindication may include a request that the parent respond by eitherauthorizing or denying the transaction.

At decision point 1110, is determined whether or not parentalauthorization is required. When parental authorization is not required,process 1100 proceeds along the “no” path to operation 1112. Atoperation 1112, the transaction between the child device and themerchant is completed. In some implementations, the transaction may becompleted based in part upon a user profile associated with the child.Furthermore, in the same or different implementations, a user profileassociated with the parent may also affect how the transaction iscompleted. For example, if the child has indicated that he or she wishesto automatically a purchase particular candy upon entering a candystore, that portion of the child's user profile may be used to completea purchase of that type of candy. The user profile associated with theparent may be used for, among other things, a source of paymentinformation to complete the candy purchase.

When parental authorization is required, the process 1100 proceeds fromdecision point 1110 along the “yes” path to decision point 1114. Atdecision point 1114, it is determined whether or not the parentalauthorization has been granted. When parental authorization is granted,for example by the parent interacting with the parent device, process1100 proceeds along the “yes” path to operation 1112 and the transactionis completed. However, when authorization is denied the process 1100proceeds along the “no” path to operation 1116 and the transaction isterminated. Termination of the transaction may result in a message beingsent to the child device and/or the merchant.

Security for Mobile Devices

FIG. 12 shows an illustrative map 1200 of temporal-geo-locations of amobile device during a workday of a user of the mobile device. Bycreating a map of where the device is typically located and when thedevice is at those locations, variance from those patterns can serve asa trigger to suggest that the device may have been stolen or misplacedand initiate a security event such as shutting down the device orrequiring a password to complete purchases with the device. This type ofsecurity feature may be implemented automatically by the device itselfbefore the user is even aware that a problem exists. The mobile devicemay include a security module 214 as illustrated in FIG. 2 forimplementing these security features.

The user may begin his workday at his home which has a fixedgeolocation. Typically he—specifically his mobile device—may be at homefrom approximately 6:00 PM until approximately 7:00 AM and thiscomprises a first temporal-geo-location 1202 for his workday. Commutingfrom home to work may involve driving along the road to work betweenapproximately 7:00 AM to approximately 7:30 AM. His automobile mayinclude an additional device, such as an on-board navigation system,that is also associated with his user identifier 208, and thus, alsocontributes to building a map of temporal-geo-locations for the user. Hemay use the same route every day in commuting to work so the systems ofthe user device may recognize this temporal-geo-location 1204 eventhough it is not a single fixed position but rather a series ofgeolocations and a series of time points. After arriving downtown, theuser's day may include another temporal-geo-location 1208 that compriseshis walk from a parking area to his office between approximately 7:30 AMand approximately 7:45 AM. While at the office the user and the userdevice may move around within the office but remain at the geolocationof the office from about 7:45 AM to about 12:00 PM. This is anothertemporal-geo-location 1210.

Up until lunchtime this user's typical weekday schedule may be fairlyconsistent. However, during lunch he may move to a variety ofgeolocations associated with various restaurants shown here asRestaurant A, Restaurant B, and Restaurant C. The user may generally beinside one of the restaurants from approximately 12:10 PM toapproximately 12:50 PM. This temporal-geo-location 1212 may have awell-defined time but a loosely defined location. For example, anygeolocation within a 10 minute walk of the office may be deemed part ofthis user's typical weekday movements during the lunch hour. After lunchthe user may return to the office. The office is at the same geolocationit was during the morning, but the time period is different so being inthe office from about 1:00 PM until about 5:00 PM creates yet anothertemporal-geo-location 1214 in the map of this user's workday.

The user may have more than one route he takes home from work. Duringthe winter, for example, the user may take a more direct road homeleaving office at about 5:10 PM and arriving home at about 6:00 PM. Thiscreates a temporal-geo-location 1214 across a range of space and timesimilar to the temporal-geo-location 1204 representing the road to work.In the summer, this user may take the scenic route home. The road homein summer may have a different geolocation in all or in part from theroad home in winter. The road home in summer may also take longer sothat while the user leaves the office at 5:10 PM he does not arrive homeuntil 6:10 PM. This creates an alternate temporal-geo-location 1216 tothe temporal-geo-location 1214 representing the road home in winter.Depending on the security settings of the mobile device, the mobiledevice may not trigger a security event no matter which route the usertakes home even if he uses the winter road during the middle of summer.Alternatively, if stricter security settings are applied then taking thesummer road during midwinter may trigger security event, but duringmid-March the mobile device may tolerate the user taking either roadwithout triggering a security event.

By recording times, dates, and geolocations as the mobile device is usedand moved it is possible for a security system, for example securitymodule 214, to learn what are typical movements through space and time.This “geolocation signature” of the user can be stored in a data file asa series of time-location data points. Some or all of these data pointsmay be layered together to create a multidimensional map containing pastgeolocation and time information for the mobile device.

FIG. 13 illustrates process 1300 for securing a mobile device based onvariance from a map of temporal-geo-locations. At operation 1302, ageolocation of the mobile device is detected. At operation 1304, a timepoint when the geolocation is detected is recorded. Next at operation1306, the geolocation is stored in association with the time point atwhich the geolocation was detected. This combination of geolocation anda time point is a temporal-geo-location. Temporal-geo-location datapoints may be recorded with varying levels of granularity based onthings such as a memory capacity of the mobile device 104, velocity atwhich the mobile device 104 is traveling, and the like. Granularity ofrecording temporal-geo-location data points may occur with a regularfrequency such as every 30 seconds or every 10 minutes. In someimplementations this data may be stored in the memory 204 of the mobiledevice 104 shown in FIG. 2. The temporal-geo-location data may bestored, among other places, as user information 210 or in the securitymodule 214 also shown above in FIG. 2.

A map is created from movements of the mobile device over time based ona plurality of the temporal-geo-locations at operation 1308. Asindicated above, this may be a multidimensional map comprising alatitude dimension, a longitude dimension, a time dimension, and a datedimension. Including additional and/or alternate dimensions in the mapis also possible. This map may become more detailed, and potentiallymore useful, as a greater amount of data is accumulated. For example,when a user initially purchases a mobile device it may not be possiblefor the mobile device to detect whether or not it has moved away fromthe user's “regular” temporal-geo map. If the user knows that he or shewill be moving in ways that are atypical (i.e., “going off the map”),the user may manually turn off the recording of temporal-geo-locationdata points. This may prevent inclusion of data into the map that woulddegrade rather than improve the accuracy of the map.

In order to detect whether or not the mobile device has been stolen,misplaced, or is otherwise in the wrong place at the wrong time,decision point 1310 may compare the current temporal-geo-location of themobile device with the map and determine whether or not the currenttemporal-geo-location varies more than a threshold amount from the map.In some implementations, this comparison may be achieved at least inpart through the use of artificial intelligence, heuristics, or fuzzylogic. In some implementations, the threshold may be configurable by theuser of the mobile device. The analysis may also draw upon calendar orscheduling information of the user to see if the user has a scheduledtrip that varies from his regular map. The calendar information may beincluded in the user information 210 and provided to the security module214.

When an amount of variance is less than the threshold amount, process1300 proceeds along the “no” path and returns to decision point 1310 toonce again query whether or not the mobile device has varied too farfrom the map. This loop may be repeated continuously, periodically, orrandomly. The frequency of repeating this loop may be based in part uponprocessor power of the mobile device 104, a velocity at which the mobiledevice 104 is moving, and/or other factors. For example, the frequencyof performing the analysis at decision point 1310 may be lower when themobile device 104 is moving at a walking pace and the frequency may behigher when the mobile device 104 is moving at a highway speed (e.g.,while in a car).

The threshold amount may also be based at least in part on the presenceof other mobile devices in the same geolocation or near to the mobiledevice. For example, a user may vary from his or her established mapduring a vacation. However, during the vacation the user may travel withhis or her family members who may have their own mobile devices. In oneimplementation, the mobile devices of the family members (or, as afurther example, coworkers) may be associated with each other. One typeof association is the parent-child relationship illustrated in FIG. 8above. The presence of these other mobile devices may be used to adjustthe threshold. The absence of other devices may also be used to adjustthe threshold. If, for example, the mobile device is rarely found in aparticular geolocation unless other mobile devices are nearby, then theabsence of those devices may be a variance from the user's map. Forexample, the mobile device associated with a parent may occasionally belocated at a soccer field on evenings during which a child is playingsoccer. However, on those evenings the child's mobile device is also atthe soccer field. If, for example, the user forgot her mobile device atthe soccer field a security event might be triggered once the child'smobile device leaves the geolocation of the soccer field. Presence orabsence of other mobile devices may comprise an additional dimension ofthe temporal-geo-location map.

Returning to process 1300, when the current temporal-geo-location variesmore than a threshold amount, process 1300 proceeds along the “yes” pathto decision point 1312. At decision point 1312 the threshold may beadjusted based on the presence of other mobile devices in the samegeolocation as the mobile device. When the threshold is adjusted,process 1300 proceeds along the “yes” path and returns to decision point1310 to reevaluate based on the adjusted threshold. When the thresholdamount of variance is not adjusted, process 1300 proceeds along the “no”path to operation 1314 and initiates a security event. The securityevent may comprise shutting down the mobile device, initiating anautomatic phone call or text message to another device that includes thecurrent location of the mobile device, requiring input of a passwordbefore the mobile device can be used, and the like. The user 104 maymanually turn off the security events if, for example, the user 104 istravelling to a new place (or travelling at a new time) and wishes toavoid “false positive” security events.

FIG. 14 illustrates process 1400 for securing a device based onbiometric data. Providing security based at least in part on biometricdata can minimize opportunities for someone other than a legitimate userof a mobile device to misuse the mobile device by, for example, makingunauthorized transactions with merchants. In order to balance betweenproviding the zero-interaction transaction experience and validating theuser's identity, biometric data may be solicited periodically such asonce per hour or once per day (or at any periodic or random time) inorder to continue using the zero-interaction transaction feature.Alternatively, in implementations in which the user makes transactionswith a single interaction, entering biometric data may comprise thatsingle interaction.

At operation 1402, biometric data is received from a sensor of themobile device. Many mobile devices, such as the mobile device 104illustrated in FIG. 2, are equipped with input devices that may be usedfor multiple purposes including receiving biometric data. For example,the mobile device 104 may include a camera 222. The mobile device mayalso include a microphone 1404. In other implementations, the inputdevice that collects biometric data may be used specifically forcollecting biometric data such as a fingerprint scanner 1406. Othertypes of general purpose input devices used to collect biometric dataand/or special-purpose biometric data input devices are also envisionedwithin the scope of this disclosure.

Next at operation 1408, the biometric data is analyzed. In someimplementations, the biometric data may be analyzed by a processor andsoftware present on the mobile device itself. This implementation mayallow the mobile device to offer stand-alone confirmation of a user'sidentity without a need to access a network or other computing device.In other implementations, the biometric data may be sent from the mobiledevice to another computing device for analysis. This implementation mayallow more sophisticated and computationally intensive techniques foranalyzing biometric data than could be readily implemented on a mobileand potentially low-power device. Analysis of the biometric data mayconvert analog input into digital data or convert a complex set of datasuch as a fingerprint into a relatively simple string of data like ahash code. The analysis of the biometric data may be matched to the typeof data received. For example, if the camera 222 is used to collectbiometric data by taking a picture of a person's face, that picture maybe analyzed using facial recognition techniques. Alternatively, if themicrophone 1404 is used to record a sample of a voice, then that datamay be analyzed by using voice recognition techniques. For added levelsof security, multiple types of biometric data may be used together suchas, for example, taking a picture of a person's face and recording thatperson's voice then analyzing both sets of biometric data.

At decision point 1410, a determination is made as to whether theanalysis of the input of biometric data matches stored biometric dataassociated with the mobile device. For example, the hash code generatedfrom a fingerprint scan could be compared to a stored hash code that theuser entered while she was setting up the mobile device. In someimplementations, the stored biometric data which is used for comparisonis stored locally on the mobile device. The biometric data may bestored, for example, as part of the user information 210 shown in FIG.2. Again, this may allow the mobile device to provide stand-aloneanalysis. In other implementations, the stored biometric data may bestored remote from the mobile device, for example, as a part of the userprofile 404 illustrated in FIG. 4. Storing the biometric data remotelymay conserve memory space on the mobile device and may provide greatersecurity by preventing an unauthorized person from extracting biometricdata from a lost or stolen mobile device.

When the analysis of the biometric data matches the stored biometricdata, process 1400 proceeds along the “yes” path and grants access to afunctionality of the mobile device at operation 1412. The functionalitymay comprise any type of operation feature, data, and the like availableon or implemented by the mobile device. For example, the ability toinitiate and complete a transaction with a merchant is one type offunctionality. The ability to make phone calls is a type offunctionality on mobile telephone devices. Associating a particularmobile device with an individual user's identity is another type offunctionality. For example, a network server such as the server(s) 118illustrated in FIG. 3 may associate a user ID (1) 208 stored on anetwork with a serial number of the mobile device based at least in partupon a login that uses biometric data. In this implementation, the usercould interact with multiple mobile devices, yet have each device tiedto his or her unique user identifier 208 and other things which arelinked to that user identifier 208 such as the payment information 402,user profile 404, and a list of trusted merchant(s) 408 as shown in FIG.4.

If, at decision point 1410 it is determined that the analyzed biometricdata does not match the stored biometric data, process 1400 may proceedalong the “no” path and initiate a security event at operation 1414. Thesecurity event may be anything from shutdown and complete deletion ofall stored data on the mobile device to a warning message displayed onthe mobile device. In some implementations, the security event may limitfunctionalities of the mobile device, such as to those functionalitythat do not incur additional charges. Other types of security events mayinclude sending an e-mail or making a phone call that communicates thecurrent location of the mobile device. The security event at operation1414 may be the same or different than the security event triggered atoperation 1314 illustrated in FIG. 13.

Security events may be triggered by other mechanisms besides variancefrom a temp oral-geo-location map or failure of a biometric login. Insome implementations, the user may be able to manually initiate asecurity event remotely from the mobile device. Some mechanisms ofachieving this include calling a phone number, sending an e-mail,entering a command from a webpage, or the like. The web page may be asecurity web page for that mobile device that shows a currentgeolocation of the mobile devices as well as past transaction data andthe like. For example, if the user suspects that his or her mobiledevice was lost or stolen that user could call a certain phone number,enter a code, and then a signal would be sent over a network andbroadcast to the mobile device causing the mobile device to temporarilyshut down. In other implementation, different triggers may be used toinitiate a security event. Some of those triggers include financialtransactions, for example, sending out an alert message when a largepurchase is initiated using the mobile device.

Advertising and Promotions

FIG. 15 shows an illustrative architecture 1500 for providing merchantadvertisements or promotions to mobile devices at or near the merchant.Mobile devices that provide the features for mobile electronic commercedescribed above may also be desirable targets for merchants to advertiseon in order to drive that mobile electronic commerce. In thearchitecture 1500, a plurality of merchants is illustrated as merchant(1) 1502, merchant (2) 1504, and merchant (N) 1506 where N may be anynumber greater than two. The merchants may submit bids 1508 to theserver(s) 118. The bids 1508 may indicate an amount of money that therespective merchants are willing to pay to have an advertisement 1510sent to a mobile device. The advertisements 1510 may be supplied by anadvertisement database 126 as illustrated in FIG. 4.

One user 102 and one mobile device 104 receiving the advertisements 1510may be the same as illustrated in FIG. 1. There may be other users 1512each having a respective mobile device 1514. Although only two users andonly two mobile devices are illustrated in FIG. 15, it is to beunderstood that any number of users and mobile devices may exist in thisarchitecture and may be appropriate recipients for an advertisement1510.

Each of the mobile devices 104 and 1514 may receive geolocationinformation from a satellite 112 or other source. The respective mobiledevices 104 and 1514 may receive geolocation information from differentsources (e.g., a radio antenna for one mobile device and a WiFi hotspotfor the other mobile device). The geolocation of the mobile devices 104and 1514 may be matched with geolocation(s) 418 associated withadvertisement content 416 as illustrated in FIG. 4. This may providelocation-relevant advertising to the mobile devices 104 and 1514.

FIG. 16 illustrates process 1600 for presenting advertisements on adevice based on bids submitted by merchants. At operation 1602, anindication of a geolocation of a mobile device is received. Thegeolocation may be determined in reference to the satellite 112illustrated in FIG. 15. At operation 1604, an advertisement preferenceof a user of the mobile device is determined. The system may beconfigured so that a user receives no advertisements unless a useraffirmatively opts in to receive advertisements. The user preferenceinformation may be part of a user profile such as user profile 404illustrated in FIG. 4. The advertisement preference may also specifywhich categories of advertisements and from which merchants the user iswilling to receive advertisements. In some implementations, a list oftrusted merchant(s) 408 may determine the merchants that are able tosend advertisements to the user. The advertising preferences maycomprise any other type of user information. For example, the userinformation may include information about past transactions between theuser and the merchant. This may be used to create targetedadvertisements, for example, by telling the user about items that he orshe purchased in the past and may wish to purchase again (e.g., talllatte) or about related items that the user may also wish to purchase(e.g., you purchased a chili dog for lunch, would you like to purchaseantacids at our nearby drugstore?).

Next, at operation 1606, merchants are identified based on thegeolocation of the mobile device and on the advertisement preference ofthe user. The identified merchants may include only merchants within aspecified distance from the mobile device. This can limit the possiblesource of advertisements to only those merchants that are locatedproximate to the geolocation of the mobile device. For example, if theuser is walking down a street lined with restaurants, restaurants alongthat street may be eligible to advertise on the mobile device butrestaurants located across town would not. A threshold or radius withinwhich merchants are identified as being proximate to the mobile devicemay vary based on the type of advertisement. For example, restaurantadvertisements may only be sent to mobile devices that are within aquarter mile of the restaurant geolocation. However, hoteladvertisements may be sent to users with mobile devices within fivemiles of the hotel geolocation. Additionally, the advertisements may besorted by time such that restaurant advertisements may be more common orcover a larger geographic area in the hours before dinner time and hoteladvertisements may cover a larger geographic area earlier in the day butprogressively narrow the geographic focus as it becomes night.

Once a pool of merchants has been identified based on at leastgeolocation and advertisement preference, bids are received from thosemerchants at operation 1608. The bids may be received and processed bythe bidding module 312 illustrated in FIG. 3. Each of the bids mayinclude different factors that the merchant is bidding on as well as amaximum bid price, a range of bid prices, or other biddingcharacteristics. For example, a merchant may bid a higher amount toplace advertisements on the mobile device of a user who has madepurchases from that merchant in the past. As a further example, themerchant may bid more to place advertisements on mobile devices that arenearer to the merchant and bid less to place advertisements on mobiledevices that are farther away from the merchant.

At operation 1610, an advertisement is selected. The selectedadvertisement may be determined based on the bid price, the userpreferences, and other factors such as, for example, whether themerchant has enough money in an advertising account to pay the bidprice. In some implementations, a winning bid that determines theselected advertisement may be the bid associated with a largest amountof money. Other bidding or auction arrangements are also possible suchas, for example, the highest bidder paying an amount bid by the secondhighest bidder.

Next, at operation 1612, the selected advertisement is presented on themobile device. The advertisement may be supplied from the advertisementdatabase 126 illustrated in FIGS. 4 and 15. More specifically, theadvertisement may be generated based on the advertisement content 416illustrated in FIG. 4. The advertisement may be presented on the mobiledevice as a banner, in a specialized ad window, or the like. In someimplementations, the advertisement may be integrated with a map so thatthe user can easily identify the location of the merchant thatcorresponds to the advertisement. The advertisements may remain on themobile device for variable periods of time. Some advertisements mayexpire after a fixed amount of time such as one minute. Advertisementsmay also expire based on geolocation of the mobile device so that whenthe mobile device leaves a geolocation near the merchant, thatmerchant's advertisement is replaced by a different advertisement.

FIG. 17 illustrates process 1700 for providing a promotion to deviceswhen a number of devices at a merchant exceeds a threshold.Advertisements may contain information touting the virtues of a merchantor the advertisements may also include a coupon or some type ofpromotion that may incentivize users to visit the merchant. Merchantsmay desire driving a large amount of traffic through their stores andchoose to structure promotions to incentivize many users to come intotheir stores at the same time. This may also contribute to a certainatmosphere or ambiance of a busy, lively merchant. Social networkingfunctionality on mobile devices may be used to spread these types ofpromotions “virally” or directly from user to user.

At operation 1702, a number of mobile devices at a merchant isdetermined based on geolocation information provided by each of themobile devices. For example, each mobile device could detect its owngeolocation based on a satellite or other system, and expose thatinformation to a server(s) 118 for inclusion in a map 310 in which thegeolocations of multiple mobile devices are correlated with thegeolocation of a merchant. The number of mobile devices may represent anumber of unique users present at that geolocation.

Next, at decision point 1704, the number of mobile devices at themerchant is compared to a threshold number. The threshold number may beset by the merchant as, for example, a number of people the merchantwould like to have on its premises. In this implementation, thethreshold may be an integer number. The threshold number may be based atleast in part on a number of mobile devices at the merchant for whichthe merchant is designated as a trusted merchant. For example, if themerchant wishes to bring in new users with the hopes that they willdesignate this merchant as a trusted merchant, the threshold may be setas a ratio such the threshold is exceeded when, for example, more than athird of all mobile devices present do not designate this merchant as atrusted merchant. When the number of mobile devices at the merchantexceeds the threshold number, process 1700 proceeds from decision point1704 along the “yes” path to operation 1706 and provides a promotion tothe users. The promotion may be a discount for a good or serviceavailable at the merchant. The promotion may be provided to all theusers present at the merchant or to only a subset. For example, toreward loyal customers, a coupon may be sent to the mobile devices ofusers who have transacted with this merchant in the past.

The promotion may be personalized for each of the users of the mobiledevices based on user information associated with the mobile device.This using information may be the same as the user information 210illustrated in FIG. 2 or the user information 122 illustrated in FIG. 4.For example, in a coffee shop each user may receive a coupon for onedollar off the coffee drink he or she has indicated as a favorite drink.Other user information may also be analyzed to personalize thepromotions. The coupon may incentivize the user to return to themerchant by providing a discount at a later time (e.g., this coupon isvalid from tomorrow for the next 10 days) or by geolocation (e.g.,please use this coupon at one of our other stores). The coupon may alsobe associated with the user identification so that the coupon is appliedautomatically the next time that user conducts a transaction with thatmerchant.

If however, the number of mobile devices at the merchant does not exceedthe threshold, process 1700 may proceed along the “no” path to operation1708 and send a message to the mobile devices. The message may be anotification of how many more devices must be present at the merchant inorder to cross the threshold. This could be a source of viral marketingby encouraging users to call or text their friends to come to thismerchant location—with their mobile devices—so that the threshold iscrossed and everybody receives the promotion. In implementations, inwhich mobile devices are counted as being at the geolocation of themerchant only when the user of that mobile device opts to expose his orher geolocation to the merchant this may encourage reticent users toshare this information in order to receive the promotion. Many otherimplementations that take advantage of the “peer pressure” effect byproviding a promotion for aggregate behavior are also possible.

There may also be instances in which a large number of customers, asindicated by a number of mobile devices, may be undesirable to themerchant and or the users. Thus in one implementation, the“advertisement” may comprise a notification about how many mobiledevices are present at a merchant and to what extent this number exceedsa maximum or threshold number. For example, a restaurant may report thatmore mobile devices are present at its geolocation than the restauranthas seats. With this information a user could be forewarned that he orshe may have to wait for a table at that restaurant. As another example,an airline may identify mobile devices of users scheduled to be on aflight that are not yet at the airport (or not within a thresholddistance of the boarding gate) to inform these users that the fight isoverbooked. This implementation may use geolocation in conjunction withuser information 122 (e.g., the flight reservation) to provide an offerto take a later flight (perhaps in exchange for an upgrade or such) tothose customers most likely to avail themselves of that offer. In theseinstances the process flow from decision point 1704 may be switched inthat the message is sent out if the number of user devices exceeds thethreshold number.

After sending the message at operation 1708, process 1700 may return tooperation 1702 and again determine a number of devices at the merchant.This may repeat until the threshold is crossed or until a period duringwhich the promotion periods ends. The process illustrated in FIG. 16 maybe combined with process 1700. For example, merchants may bid for theright to send an advertisement that comprises a promotion.

CONCLUSION

These processes discussed above are each illustrated as a collection ofblocks in a logical flow graph, which represent a sequence of operationsthat can be implemented in hardware, software, or a combination thereof.In the context of software, the blocks represent computer-executableinstructions stored on one or more computer-readable storage media that,when executed by one or more processors, perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures, and the like that performparticular functions or implement particular abstract data types. Theorder in which the operations are described is not intended to beconstrued as a limitation, and any number of the described blocks can becombined in any order and/or in parallel to implement the process.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as illustrative forms ofimplementing the claims.

1. A computing device comprising: one or more processors; and a memorycoupled to the one or more processors, the memory comprising: aplurality of user profiles each associated with a respective useridentifier and a respective mobile device; a plurality of merchantprofiles, each associated with a one or more geolocations; and atransaction module configured to facilitate a transaction at thegeolocation of a merchant between a user of a mobile device and themerchant when a geolocation of the mobile device is within a thresholddistance of the geolocation of the merchant and a user profile of theuser indicates that the merchant is a trusted merchant for the user,wherein trusted merchants are authorized to implement a defaulttransaction with the user, the default transaction comprises purchasinga good or service by providing payment information associated with theuser profile of the user to the merchant, wherein the paymentinformation is specified in advance by the user.
 2. The computing deviceas recited in claim 1, wherein the user profiles comprise userpreferences, indications of which types of communications the user hasselected to receive, and/or indications which types of transactions theuser has selected to authorize.
 3. The computing device as recited inclaim 1, wherein the transaction module is further configured to add thegeolocation and a record of the transaction to a user profile associatedwith a user identifier of the user that participated in the transaction.4. The computing device as recited in claim 1, wherein the transactionmodule is further configured with application programming interfaces forexchanging information with both mobile devices and merchants.
 5. Thecomputing device as recited in claim 4, wherein the applicationprogramming interfaces translate communications between the mobiledevices and the merchants.
 6. The computing device as recited in claim1, wherein the memory further comprises a map of merchant locationsbased on the one or more geolocations stored in the plurality ofmerchant profiles.
 7. The computing device as recited in claim 1,wherein the threshold distance is determined at least in part bycomparison of the geolocation of the mobile device with the map ofmerchant locations.
 8. The computing device as recited in claim 1,wherein the memory further comprises an authentication module configuredto correlate, based in part on login information provided by the user ofthe mobile device, a user identifier with communications from the mobiledevice.
 9. A mobile device comprising: one or more processors; alocation sensor coupled to the one or more processors; a wirelessnetwork interface coupled to the one or more processors; and a memorycoupled to the one or more processors, the memory comprising: a useridentification module correlated with user information comprisingpayment information and trust levels for one or more merchants, the userinformation available on a network accessed by the wireless networkinterface; and a transaction module configured to interpret data fromthe location sensor, to recognize when the mobile device is presentwithin a predetermined proximity of a merchant of the one or moremerchants, and, based at least in part on recognizing that the mobiledevice is present within the predetermined proximity of the merchant andin response to user interaction with the mobile device, an amount of theuser interaction being based at least in part on the trust level for themerchant using the payment information.
 10. The mobile device as recitedin claim 9, wherein the mobile device comprises an electronic bookreader device.
 11. The mobile device as recited in claim 9, wherein thelocation sensor comprises a global positioning system receiver.
 12. Themobile device as recited in claim 9, wherein the location sensor isconfigured to infer a location of the mobile device based on informationprovided by the wireless network interface.
 13. The mobile device asrecited in claim 9, wherein the transaction module authorizes atransaction with a merchant having a highest trust level automaticallywhen the mobile device is within the predetermined proximity of themerchant and without further input from a user of the mobile device. 14.The mobile device as recited in claim 9, wherein the transaction modulefurther comprises application programming interfaces configured toestablish a standard communication protocol for transferring databetween the mobile device and the merchant.
 15. The mobile device asrecited in claim 9, wherein the memory further comprises userinformation stored locally on the mobile device.
 16. The mobile deviceas recited in claim 9, wherein the transaction module authorizes atransaction with a merchant having a medium trust level in response to asingle interaction from the user of the mobile device when the mobiledevice is within the predetermined proximity of the merchant.
 17. Themobile device as recited in claim 16, further comprising a microphoneand wherein the single transaction comprises a voice command.
 18. Themobile device as recited in claim 16, further comprising anaccelerometer and wherein the single transaction comprises shaking themobile device.
 19. The mobile device as recited in claim 9, wherein thetransaction module authorizes a transaction with a merchant having alowest trust level in response to receiving login information from theuser of the mobile device when the mobile device is within apredetermined proximity of the merchant.